Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
Important: Both peers must be using the same address family (IPv4 or IPv6) or the SRP connection will not establish.bind address 1.1.1.1
checkpoint session duration duration
The amount of time (in seconds) that a call must be active before it is check pointed. duration must be an integer from 1 through 65535.
configuration-interval interval
The amount of time (number of seconds) between one configuration validation and the next configuration validation. interval must be an integer from 1 through 65535.
dead-interval interval
The amount of time (in seconds) for the dead interval. interval must be an integer from 1 through 65535.
delay-intervalinterval
The amount of time (in seconds) for the delay interval. interval must be an integer from 1 through 65535.
hello-interval interval
The lapse time (in seconds) between sending the hello message. interval must be an integer from 1 through 65535.
internal-switchover-retry-interval interval
The amount of time (number of seconds) between internal switchover retries. interval must be an integer from 10 through 120.
Important: See the monitor authentication-probe, monitor bgp, or monitor diameter commands for more information on associated SRP monitoring.[ no ] monitor authentication-probe context context_name { IPv4_address | IPv6_address } [ port port_number ]
context context_name
Identifies the context being used. context_name must be an existing context and between 1 and 79 alpha and/or numeric characters.
port port_number
Identifies a specific port for the authentication probe. port_number must be the port for the AAA server and an integer from 1 to 65535.
The following example initiates the connection monitoring between the primary chassis and AAA server 1.2.3.4 at port 1025:
context context_name
Identifies the context being used. context_name must be an existing context and between 1 and 79 alpha and/or numeric characters.
vrf vrf_name
The following example initiates the connection monitoring between the primary chassis and BGP peer 125.2.1.56:
monitor bgp context test 125.2.1.56
[ no ] monitor diameter context context_name endpoint endpoint_name [ fqdn fqdn | peer { IPv4_address | IPv6_address } ] [ port port_number ]
context context_name
Identifies the context being used. context_name must be an existing context and between 1 and 79 alpha and/or numeric characters.
endpoint endpoint_name
Identifies the endpoint being used. endpoint_name must be for the DIAMETER server and between 1 and 63 alpha and/or numeric characters.
fqdn fqdn
Identifies a Fully Qualified Domain Name (FQDN). fqdn must be for the DIAMETER server and between 1 and 127 alpha and/or numeric characters.
port port_number
Identifies a specific port to monitor. port_number must be the port for the DIAMETER server and an integer from 1 to 65535.
Important: Endpoint name, FQDN, IP address, and port must all match the DIAMETER protocol configured values for the peer state to be updated.The following example initiates the connection monitoring between the primary chassis and the DIAMETER server on context test1 and endpoint end2:
num-internal-switchover-retry retries
The number of times an internal switchover would be retried in case of standby chassis. retries must be an integer from 1 through 10.
Important: Both peers must be using the same address family (IPv4 or IPv6) or the SRP connection will not establish.The following example specifies 1.2.3.4 as a backup peer system to the primary system:
peer-ip-address 1.2.3.4
Important: priority takes affect only during simultaneous initializing of all chassis in an ICSR configuration, and only if a misconfiguration has both chassis in the same mode (both Primary or both Backup).priority priority_value
The priority for the chassis. priority_value must be an integer from 1 through 255.
This command determines which chassis transitions to the Active state when all chassis have the same mode configuration. priority acts as a tie breaker for the state determination only when all chassis initialize simultaneously. The chassis with the higher priority (higher number) becomes Active while the chassis with the lower priority (lower number) becomes Standby.
priority 5
route-modifier threshold threshold_value
The value that causes the route-modifier counter to be reset to the initial value. threshold_value must be an integer from 2 through 32.
